Provisioning an embedded subscriber identity module

ABSTRACT

Provisioning an embedded subscriber identity module (eSIM) in a user equipment (UE) device with personalized subscriber information. A request may be transmitted for personalized subscriber information. The personalized subscriber information may be received. The personalized subscriber information may be installed in an eSIM in the UE device.

PRIORITY CLAIM

The present application claims benefit of priority to U.S. ProvisionalApplication No. 61/646,046 titled “Provisioning an Embedded SubscriberIdentity Module” and filed on May 11, 2012, whose inventors are Li Li,Arun G. Mathias, and Ben-Heng Juang, and which is hereby incorporated byreference in its entirety as thought fully and completely set forthherein.

FIELD

The present application relates to the field of wireless communication,and more particularly to a system and method for provisioning anembedded subscriber identity module (eSIM) in a user equipment (UE)device.

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. Further,wireless communication technology has evolved from voice-onlycommunications to also include the transmission of data, such asInternet and multimedia content.

Subscribers in a wireless telecommunication network (e.g., a cellulartelecommunication network) are typically assigned subscriber identityinformation, which may for example be stored as part of a subscriberidentity module (SIM) in the subscriber's user equipment (UE) device. Asone example, subscribers in 3GPP (LTE/GSM/UMTS) networks have anInternational Mobile Subscriber Identity (IMSI) that identifies them intheir carrier's network.

It is common practice for a SIM to be installed on a physical chip orcard, which may be provided separately from a UE. Thus, in order toobtain a UE and be provided with service for the UE, a user may need toobtain the UE (e.g., from a wireless device vendor) and separatelyobtain a SIM card (e.g., from a service provider) and install it in theUE. Requiring multiple steps and interaction with both a wireless devicevendor and a service provider in order to obtain service for a UE may bean annoyance for the end user. In addition, the requirement that a userremove the old SIM card, obtain a new physical SIM card, and install thenew SIM card in order to change service providers may represent anadditional cause of frustration to end users, and may represent apsychological barrier to switching service providers, which mayindirectly result in higher costs and/or lower quality of service forthe user.

The practice of using removable physical SIM cards also leaves much tobe desired for service providers. As one example, using this approachrequires service providers to manufacture and/or order the physical SIMcards, which represents a significant expense. In addition, keeping aninventory of physical SIM cards represents an additional set ofexpenses, both in terms of storage and shipping, and in terms ofinventory management. Furthermore, the SIM cards may need to beprovisioned well in advance of their use, which may represent anadditional expense, as some or all of the provisions (e.g., IMSIs, etc.)may have a cost basis. Thus, a SIM card which sits in inventory and isnot used may represent a wasted expense for service providers for avariety of reasons.

Accordingly, considering the non-trivial disadvantages of removablephysical SIM cards, improvements in the field would be desirable.

SUMMARY

Various embodiments are presented of a system and method for obtainingand personalizing an embedded subscriber identity module (eSIM) in auser equipment (UE) device. In particular, use of an eSIM in a UEdevice, which may be personalized (e.g., provisioned and activated)over-the-air (OTA), may represent a considerable improvement overpre-provisioned, removable, physical SIM cards.

For example, user experience may be improved by the use of an eSIM intheir UE device. Rather than separately obtaining the physical UE deviceand a physical SIM card, then installing the SIM card into the UEdevice, the user may be able to just obtain the UE device, which mayhave hardware capable of supporting an eSIM pre-installed. Furthermore,selection of a service provider may be simplified, and the process ofswitching service providers may be significantly eased. For example, auser may be able to more easily compare service providers' coverage andplans and/or select a plan if the provisioning process is performed overa network (and particularly if the provisioning process is performedOTA, and thus potentially in any location with wireless service), ratherthan in a service provider store location which only offers plans fromthat service provider. Along the same lines, re-provisioning an eSIMover a network (potentially including OTA) may be a simpler process ofswitching service providers than going into a service provider'sstorefront and/or waiting for delivery to obtain a new physical SIM,removing the old SIM, and installing the new SIM.

Additionally, service providers may realize a more efficient andcost-effective mechanism for provisioning UE devices with service.Because manufacture, storage, shipping, and provisioning of physical,removable SIM cards all represent real costs to service providers whichmay be eliminated and replaced with a relatively cost-efficientnetwork-based just-in-time provisioning process, overall costs may besignificantly reduced. Reduced operating costs of physical storefrontsmay also be possible, in some cases, as more plans are sold OTA andfewer personnel and/or storefronts are required to sell service plansand corresponding removable SIM cards.

Furthermore, embodiments may comprise separating SIM provisioning intotwo portions—e.g., common SIM information, which may be common to someor all SIMs according to various types or classes (e.g., based onservice provider, device hardware, or other factors), and personalizedSIM information, which may be specific to a subscriber—which may offerfurther flexibility and efficiency in eSIM provisioning. For example, ifcommon SIM information is pre-loaded into applicable UE devices, asignificant amount of network bandwidth may be saved, as this portion ofthe SIM may typically be significantly larger than the personalized SIMinformation. Other benefits will also be apparent to those of skill inthe art in light of this disclosure.

The present disclosure is thus directed to such a method forprovisioning an eSIM in a UE device, to a UE device configured toimplement such a method, and/or to a computer accessible memory mediumstoring program instructions executable by a processor to implement sucha method.

The UE device may include one or more antennas for performing wirelesscommunication. The UE device may also include a processor configured toexecute program instructions. In addition, the UE device may include anon-transitory computer accessible memory medium, which may storeprogram instructions executable by the UE device. The method may beperformed as follows.

A request to provision the eSIM may be transmitted. The request may beprovided by the UE device to a first server. The request may betransmitted wirelessly (e.g., via a carrier network or a wi-fi accesspoint) or in a wired manner (e.g., via Ethernet, optic cables, etc) overone or more networks (e.g., LAN, WAN, cellular network, WLAN, WiMAX,etc).

The request to provision the eSIM may include a single request for bothcommon SIM information and personalized SIM information, or individualrequests for common SIM information and/or for personalized SIMinformation. For example, the eSIM may include the common SIMinformation pre-loaded or pre-installed in the eSIM on the UE device; insuch cases, the UE device might only request the personalized SIMinformation.

The common SIM information may be for provisioning the eSIM on the UEdevice with non-subscriber-specific information, while the personalizedSIM information may be for provisioning the eSIM on the UE device withsubscriber-specific information.

The first server may transmit the common SIM information to the UEdevice, e.g., if the common SIM information is not pre-loaded in the UEdevice. The UE device may receive the common SIM information from thefirst server and install the common SIM information in the eSIM on theUE device. The UE device may transmit an indication that the common SIMinformation has been installed on the UE device.

The first server may transmit a request for personalized SIM informationto a second server. In some embodiments, the first server may transmitthe request for personalized SIM information to the second server inresponse to receiving the indication that the common SIM information hasbeen installed on the UE device.

Alternatively, the UE device may transmit the request for personalizedSIM information directly to the second server. The second server maytransmit the personalized SIM information to the UE device (or to thefirst server, which may transmit the personalized SIM information to theUE device). In either case, the UE device may receive the personalizedSIM information.

If desired, the personalized SIM information may be encrypted, e.g.,using a carrier key. Thus, the personalized SIM information may betransmitted to the UE device in encrypted form. The carrier key may beprovided to the UE device as part of the common SIM information, or inanother way. If the personalized SIM information is encrypted, the UEdevice may decrypt the personalized SIM information, e.g., using thecarrier key provided to the UE device as part of the common SIMinformation.

The UE device may install the personalized SIM information in the eSIMon the UE device. Note that the eSIM may be stored in the UE device inmultiple ways. For example, the eSIM may be stored on an embedded smartcard (e.g., an eUICC). Additionally, part or all of the eSIM may beinstalled and stored in device memory and executed by a device processor(e.g., an application processor). Note also that in some embodiments,the UE may install the personalized SIM information in a SIM on aremovable smart card (e.g., a removable UICC).

Once the common SIM information and the personalized SIM informationinstalled in the eSIM in the UE device, the UE device may be fullyprovisioned, and the UE device may be able to access a carrier networkusing the eSIM.

If desired, the method may further include re-provisioning or requestingadditional provisioning for the eSIM. For example, a user may wish tochange their carrier or be provided with additional service from anothercarrier. In this case, a second request for provisioning information forthe eSIM may be transmitted, e.g., to the eSIM server (or a differenteSIM server). In response, second personalized SIM information (andpossibly second common SIM information) may be received by the UEdevice. The second personalized SIM information (and second common SIMinformation, if applicable) may be installed in the eSIM. The firstpersonalized SIM information may be removed from the eSIM (e.g., if theuser is no longer a subscriber with a carrier which provided the firstpersonalized SIM information) or may remain in the eSIM along with thesecond personalized SIM information (e.g., if the user is a subscriberwith both the carrier which provided the first personalized SIMinformation and the carrier which provided the second personalized SIMinformation).

Thus the disclosure herein is also directed to a method for provisioningeSIMs, a computer system configured to implement such a method, and/orto a computer accessible memory medium storing program instructionsexecutable by a processor to implement such a method. The method may, asone example, be implemented by an eSIM server. The method may beperformed as follows.

A request to provision an eSIM may be received. The request may bereceived from a UE device. The request may be received via one or morenetworks, such as one or more wired or wireless networks.

Common SIM information may be transmitted to the UE device. The UEdevice may install the common SIM information and transmit an indicationthat the common SIM information has been installed, which may bereceived.

A request for personalized SIM information may be transmitted to apersonalization server. In some embodiments, the request may betransmitted based at least in part on receiving the indication from theUE device that the common SIM information has been installed.

The personalized SIM information may be received from thepersonalization server. If desired, the personalized SIM information maybe received in encrypted form. The personalized SIM information may thenbe transmitted to the UE device. If the personalized SIM information wasreceived in encrypted form, the personalized SIM information may also betransmitted in encrypted form.

An indication that the personalized SIM information has been installedmay be received from the UE device. The common SIM information and thepersonalized SIM information may be configured to provision an eSIM inthe UE device. Thus, after the common SIM information and thepersonalized SIM information have been installed in the UE device, theUE device's eSIM may be fully provisioned. The (e.g., fully provisioned)eSIM may enable the UE device to access a carrier network.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of the preferred embodiment isconsidered in conjunction with the following drawings, in which:

FIG. 1 illustrates an exemplary (and simplified) wireless communicationsystem according to one embodiment;

FIG. 2 illustrates a base station in communication with user equipmentaccording to one embodiment;

FIG. 3 illustrates an exemplary block diagram of a user equipmentdevice, according to one embodiment;

FIG. 4 is a flowchart diagram illustrating a method for personalizing aneSIM in a user equipment device according to one embodiment; and

FIG. 5 illustrates an exemplary flow representing a process forpersonalizing an eSIM according to one embodiment.

While the features described herein are susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Acronyms

The following acronyms are used in the present patent application.

3GPP: Third Generation Partnership Project

3GPP2: Third Generation Partnership Project 2

GSM: Global System for Mobile Communications

UMTS: Universal Mobile Telecommunications System

LTE: Long Term Evolution

SIM: Subscriber Identity Module

eSIM: Embedded SIM

UICC: Universal Integrated Circuit Card

eUICC: Embedded UICC

IMSI: International Mobile Subscriber Identity

MCC: Mobile Country Code

MNC: Mobile Network Code

PIN: Personal Identification Number

PUK: Personal Unblocking Code

OTA: Over-The-Air

HLR: Home Location Register

Terms

The following is a glossary of terms used in the present application:

Memory Medium—Any of various types of memory devices or storage devices.The term “memory medium” is intended to include an installation medium,e.g., a CD-ROM, floppy disks 104, or tape device; a computer systemmemory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM,Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media,e.g., a hard drive, or optical storage; registers, or other similartypes of memory elements, etc. The memory medium may comprise othertypes of memory as well or combinations thereof. In addition, the memorymedium may be located in a first computer system in which the programsare executed, or may be located in a second different computer systemwhich connects to the first computer system over a network, such as theInternet. In the latter instance, the second computer system may provideprogram instructions to the first computer system for execution. Theterm “memory medium” may include two or more memory mediums which mayreside in different locations, e.g., in different computer systems thatare connected over a network. The memory medium may store programinstructions (e.g., embodied as computer programs) that may be executedby one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), personal communication device, smart phone, televisionsystem, grid computing system, or other device or combinations ofdevices. In general, the term “computer system” can be broadly definedto encompass any device (or combination of devices) having at least oneprocessor that executes instructions from a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™,iPhone™), laptops, PDAs, portable Internet devices, music players, datastorage devices, or other handheld devices, etc. In general, the term“UE” or “UE device” can be broadly defined to encompass any electronic,computing, and/or telecommunications device (or combination of devices)which is easily transported by a user and capable of wirelesscommunication.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thusthe term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

FIGS. 1-2—Communication System

FIG. 1 illustrates an exemplary (and simplified) wireless communicationsystem. It is noted that the system of FIG. 1 is merely one example of apossible system, and embodiments may be implemented in any of varioussystems, as desired.

As shown, the exemplary wireless communication system includes a basestation 102 which communicates over a transmission medium with one ormore user devices 106-1 through 106-N. Each of the user devices may bereferred to herein as a “user equipment” (UE). Thus, the user devicesare referred to as UEs or UE devices.

The base station 102 may be a base transceiver station (BTS) or cellsite, and comprises hardware that enables wireless communication withthe user devices 106-1 through 106-N. The base station 102 may also beequipped to communicate with a network 100. Thus, the base station 102may facilitate communication between the user devices and/or between theuser devices and the network 100.

The base station 102 and the user devices may be configured tocommunicate over the transmission medium using any of various wirelesscommunication technologies or telecommunication standards such as GSM,CDMA, WLL, WAN, WiFi, WiMAX etc. Base station 102 and other similar basestations operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UE106 and similar devices over a wide geographic area via one or morecellular communication standards.

UE 106 may be capable of communicating using multiple wirelesscommunication standards. For example, UE 106 might be configured tocommunicate using either of a 3GPP telecommunication standard (such asLTE) or a 3GPP2 telecommunication standard (such as CDMA2000). UE 106might also or alternatively be configured to communicate using WLAN,Bluetooth, one or more global navigational satellite systems (GNSS,e.g., GPS or GLONASS), one and/or more mobile television broadcastingstandards (e.g., ATSC-M/H or DVB-H), etc. Other combinations of wirelesscommunication standards (including more than two telecommunicationstandards) are also possible.

FIG. 2 illustrates user equipment 106 (e.g., one of the devices 106-1through 106-N) in communication with the base station 102. The UE 106may be a device with wireless network connectivity such as a mobilephone, a hand-held device, a computer or a tablet, or virtually any typeof wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodsembodiments described herein by executing such stored instructions. Insome embodiments, the UE 106 may include a programmable hardware elementsuch as an FPGA (field-programmable gate array) that is configured toperform any of the method embodiments described herein, or any portionof any of the method embodiments described herein.

In some embodiments, the UE 106 may be configured to communicate usingany of multiple wireless communication protocols. For example, the UE106 may be configured to communicate using two or more of CDMA 2000,LTE, WLAN, or GNSS. Other combinations of wireless communicationstandards are also possible.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols. In some embodiments, the UE106 may share one or more parts of a receive and/or transmit chainbetween multiple wireless communication standards. The shared radio mayinclude a single antenna, or may include multiple antennas (e.g., forMIMO) for performing wireless communications. Alternatively, the UE 106may include separate transmit and/or receive chains (e.g., includingseparate antennas and other radio components) for each wirelesscommunication protocol with which it is configured to communicate. Asanother alternative, the UE 106 may include one or more radios which areshared between multiple wireless communication protocols, and one ormore radios which are used exclusively by a single wirelesscommunication protocol. For example, the UE 106 may include a sharedradio for communicating using either of LTE or 1xRTT, and separateradios for communicating using each of Wi-Fi and Bluetooth. Otherconfigurations are also possible.

FIG. 3—Exemplary Block Diagram of a UE

FIG. 3 illustrates an exemplary block diagram of a UE 106. As shown, theUE 106 may include a system on chip (SOC) 200, which may includeportions for various purposes. For example, as shown, the SOC 200 mayinclude processor(s) 202 which may execute program instructions for theUE 106 and display circuitry 204 which may perform graphics processingand provide display signals to the display 240. The processor(s) 202 mayalso be coupled to memory management unit (MMU) 240, which may beconfigured to receive addresses from the processor(s) 202 and translatethose addresses to locations in memory (e.g., memory 206, read onlymemory (ROM) 250, NAND flash memory 210) and/or to other circuits ordevices, such as the display circuitry 204, radio 230, connector I/F220, and/or display 240. The MMU 240 may be configured to perform memoryprotection and page table translation or set up. In some embodiments,the MMU 240 may be included as a portion of the processor(s) 202.

In the embodiment shown, ROM 250 may include a bootloader 252, which maybe executed by the processor(s) 202 during boot up or initialization. Asalso shown, the SOC 200 may be coupled to various other circuits of theUE 106. For example, the UE 106 may include various types of memory(e.g., including NAND flash 210), a connector interface 220 (e.g., forcoupling to the computer system), the display 240, and wirelesscommunication circuitry (e.g., for LTE, CDMA2000, Bluetooth, WiFi,etc.).

The UE device 106 may include at least one antenna, and possiblymultiple antennas, for performing wireless communication with basestations and/or other devices. For example, the UE device 106 may useantennas 235 and 237 to perform the wireless communication. The UE maybe configured to communicate wirelessly using multiple wirelesscommunication standards in some embodiments.

As described herein, the UE 106 may include hardware and softwarecomponents for operating a UE device which is configured to provision aSIM or an eSIM in the UE device according to embodiments of thisdisclosure.

As shown, the UE 106 may include a SIM (Subscriber Identity Module) 310.The SIM may be implemented as an application on a smart card, in someembodiments. The smart card may itself be referred to as a SIM card insome cases. As one example, the SIM 310 may be an application whichexecutes on a Universal Integrated Circuit Card (UICC). The smart cardmay also include (e.g., store and/or execute) one or more otherapplications, if desired. The smart card may be removable.

Alternatively, the SIM may be implemented as an embedded SIM (eSIM). Inthis case, the SIM may be implemented in device hardware and/orsoftware. For example, in some embodiments, the UE 106 may include anembedded UICC (eUICC), e.g., a device which is built into the UE 106 andis not removable. The eUICC may be programmable, such that an eSIM maybe implemented on the eUICC. In other embodiments, the eSIM may beinstalled in UE 106 software, e.g., as program instructions stored on amemory medium (such as memory 206) executing on a processor (such asprocessor 202) in the UE 106.

Note that a SIM may also or alternatively be installed on a removablesmart card (e.g., a removable SIM card) according to embodiments of thisdisclosure if desired; for example, a SIM might be installed on aremovable UICC and provisioned and/or re-provisioned over a network(e.g., over-the-air (OTA)). Thus, although some aspects of thedisclosure are described primarily with reference to provisioning aneSIM, it should be recognized that at least some such aspects may bemodified for use in provisioning a SIM on a removable smart card, e.g.,in a similar manner, if desired.

The SIM 310 may include a number of types of information, includingpersonalized information specific to a user and/or device (e.g.,personalized information), and information that is not specific to auser and/or device (e.g., common information). The common portion mayinclude files, data structures, and/or applications that may be commonamong some or all types of SIMs (e.g., among UICCs/eUICCs of the sameprofile). The personalized information may include user/unit specificdata, for example information identifying the user/unit to theircarrier's network, personalized authorization and/or securityinformation, etc.

As one example, the personalized information may include anInternational Mobile Subscriber Identity (IMSI) number which identifiesthe subscriber to their carrier's network. The IMSI may, for example, bea number including the subscriber's “home” mobile country code (MCC) andmobile network code (MNC), as well as a Mobile SubscriptionIdentification Number (MSIN) which is unique to the subscriber. Thepersonalized information may also or alternatively include a personalidentification number (PIN) (e.g., a code which the user may use toaccess their SIM), a personal unblocking code and/or personal unblockingkey (PUC/PUK), and one or more authentication keys (K/Ki). Any of avariety of other personalized information may also or alternatively beused, as desired.

As noted above, the UE device 106 may be configured for use with an eSIMin some embodiments. The UE device 106 may initially include an eSIMwhich is partially provisioned (e.g., with common SIM information), ormay not yet include an eSIM. In either case, a mechanism may benecessary to provision the UE device 106 with at least the personalizedportion of the eSIM. FIG. 4 and the description provided with respectthereto relate to one such method for provisioning an eSIM in a UEdevice with personalized information.

The processor 202 of the UE device 106 may be configured to implementpart or all of the methods described herein, e.g., by executing programinstructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium). In other embodiments, processor 202may be configured as a programmable hardware element, such as an FPGA(Field Programmable Gate Array), or as an ASIC (Application SpecificIntegrated Circuit).

FIG. 4—Flowchart

FIG. 4 is a flowchart diagram illustrating a method for provisioning aneSIM in a UE device with personalized information according to one setof embodiments. The method may be implemented, at least partially, by aUE device. Some aspects of the method may be implemented by one or moreserver computers. For example, the UE device may be configured torequest SIM provisioning information from one or more servers, which mayprovide the SIM provisioning information to the UE device. The UE devicemay then install and/or provision an eSIM on the UE device with the SIMprovisioning information. The process may provide numerous benefits overa statically provisioned, physical, removable SIM card.

The method shown in FIG. 4 may be used in conjunction with any of thesystems or devices shown in the above Figures, among other devices. Invarious embodiments, some of the method elements shown may be performedconcurrently, in a different order than shown, or may be omitted. Notealso that additional method elements may also be performed as desired.

The UE device may obtain common SIM information. The common SIMinformation may be configured for provisioning the eSIM on the UE devicewith non-user specific information, in some embodiments. In other words,the common SIM information might include files, data structures, and/orapplications that may be common among some or all types of SIMs. Forexample, address book data structures and/or applications, might beincluded in the common SIM information. The common SIM information mightalso include applications or files for use in conjunction withpersonalized SIM information, in some embodiments, and/or firmware orsoftware for configuring a certain type or class of smart card (e.g., toconfigure an eUICC on which the eSIM will be stored/executed). In oneexemplary embodiment, the common SIM information may include carrier OTAkeys for decrypting personalizing SIM information (and/or for otherpurposes).

The common SIM information may be obtained by the UE device in any of avariety of ways. According to one set of embodiments, the UE device maybe pre-loaded/pre-configured with some or all of the common SIMinformation. For example, a UE device which includes a certain type ofeUICC may be configured with information specific to executing an eSIMon that eUICC, and/or certain common SIM information may be installed onthe UE device at the same time as operating system (OS) software.

Alternatively, or in addition, some or all of the common SIM informationmay be obtained via a network or combination of networks. The network(s)may be any type of network(s), including a cellular service provider'snetwork, a wired or wireless local area network (LAN), a wide areanetwork, etc.

Note that a SIM may in some cases be required to access a cellularservice provider's network. In order to facilitate eSIM provisioningover a cellular network, the UE device may thus in some cases initiallybe provided with a “bootstrap eSIM”, which may provide (e.g., limited)access to a carrier's network. For example, the bootstrap eSIM mayprovide access to a network only for the purpose of provisioning aneSIM. The user may then initiate embodiments of the presently disclosedmethod for provisioning an eSIM via the carrier's network. In someembodiments, the eSIM provisioned via embodiments of the presentlydisclosed method may provide access to a different carrier network(e.g., a different service provider's network) than the bootstrap eSIM.Of course it should also be noted that other means of provisioning aneSIM according to the presently described method, such as via a wired orwireless home internet connection, are also possible.

Thus, in some embodiments, once a user acquires their UE device, theymay contact an eSIM provider (e.g., via the UE device), such as aservice provider/carrier, and request eSIM provisioning for their UEdevice. Thus, the UE device may transmit a request for eSIMprovisioning.

The request may be provided to a first server (an “eSIM server”). Thefirst server may, for example, be operated by the eSIM provider (e.g., aservice provider). The first server may be provide some or all of thecommon SIM information to the UE device (e.g., via the network/OTA).

In 402, then, the UE device may install the common SIM information in aneSIM on the UE device. Installing the common SIM information may providebasic structure for the eSIM, in some embodiments. The eSIM may beinstalled in/stored in/executed by a smart card (e.g., an embedded smartcard, such as an eUICC) on the UE device. Alternatively, the eSIM may beinstalled and stored in device memory and executed by a device CPU. Asanother alternative, the eSIM may be installed/stored/executed by acombination of a smart card, device memory, and a device CPU. Note alsothat if desired, the UE device may install the common SIM information ina SIM which is not embedded on the UE device, e.g., on a removable smartcard, such as a removable UICC.

The UE device may provide an indication that installation of the commonSIM information was successful. This may be important, as in some casessuccessful installation of the common SIM information may be requiredbefore personalized SIM information may be used; for example, common SIMinformation might include information required to install or use thepersonalized SIM information. The indication may be provided to the eSIMserver.

In 404, personalized SIM information may be requested. The request forpersonalized SIM information may be included inherently in the requestfor eSIM provisioning. For example, the request for eSIM provisioningmay include a request for both common SIM information and personalizedSIM information. Alternatively, a request may be made for just thepersonalized SIM information. For example, if the common SIM informationis pre-loaded in an eSIM in the UE device, the UE device may only makean OTA request for the personalized UE information.

The request for personalized SIM information may be transmitted over anetwork or combination of networks. The request for personalized SIMinformation may be transmitted to the first server (e.g., as part of therequest for eSIM provisioning), or alternatively, may be transmitted toa second server (a “personalization server”). In other words, in someembodiments, the eSIM provider may operate an eSIM server (e.g.,responsible for providing common SIM information) and a personalizationserver (e.g., responsible for providing personalized SIM information).In some embodiments, the request for personalized SIM information may betransmitted to the eSIM server along with the request for common SIMinformation (or independently of the request for common SIMinformation), and the eSIM server may transmit the request forpersonalized SIM information to the personalization server.

The personalization server may provide the personalized SIM information.The personalized SIM information may include any of a variety ofinformation, according to various embodiments. Generally, thepersonalized SIM information may be configured for provisioning the eSIMon the UE device with user (subscriber) specific information. Forexample, the personalized SIM information may include an InternationalMobile Subscriber Identity (IMSI) number, a personal identificationnumber (PIN), a personal unblocking key (PUK), and one or moreauthorization keys (e.g., a K/Ki set).

The personalization server may generate the personalized SIM informationin response to the request for personalization information, in someembodiments. Alternatively, personalization information may bepre-generated, e.g., to reduce network load.

The personalization server may interact with a home location register(HLR) and provisioning system of the service provider/carrier, in someembodiments. For example, prior to providing the personalized SIMinformation to the UE device, it may be desirable to activate servicefor the particular set of personalized SIM information which will beprovided to the UE device, so that the UE device may be provided withservice upon finishing provisioning of its eSIM. Thus, in someembodiments, the personalization server may send a request to anHLR/provisioning system to activate service for the set of personalizedSIM information. The HLR/provisioning system may then activate servicefor the set of personalized SIM information and provide an indicationthat activation was successful to the personalization server.

The personalized SIM information may be provided to the UE directly(e.g., if the request was provided from the UE to the personalizationserver) or to the eSIM server (e.g., if the request was passed from theeSIM server to the personalization server) and thence to the UE device,in various embodiments.

In some embodiments, the personalization server may encrypt thepersonalized SIM information. For example, the personalized SIMinformation may be encrypted using carrier OTA keys. The carrier OTAkeys might be included in the common SIM information, and may thus beavailable to the UE device to decrypt the personalized SIM information.Other ways of encrypting the personalized SIM information are alsopossible. Encrypting the personalized SIM information may be desirableparticularly if the personalized SIM information is routed through theeSIM server, e.g., in order to prevent the eSIM server from peeking intoplain-content personalized SIM information.

In 406, the personalized SIM information may be received by the UEdevice. The personalized SIM information may be received from the eSIMserver or from the personalization server. As noted above, in someembodiments, the personalized SIM information may be encrypted, e.g.,using a carrier's OTA key(s). In such embodiments, the UE device maydecrypt the personalized SIM information.

In 408, the personalized SIM information may be installed in the eSIM.As noted above, the eSIM may be installed in/stored in/executed by asmart card (e.g., an embedded smart card, such as an eUICC) on the UEdevice, in some embodiments. In other embodiments, the eSIM may beinstalled and stored in device memory and executed by a device CPU. Instill other embodiments, the eSIM may be installed/stored/executed by acombination of a smart card, device memory, and a device CPU. It shouldalso again be noted that in some embodiments the UE device mayalternatively install the personalized SIM information in a SIM which isnot embedded on the UE device, e.g., on a removable smart card, such asa removable UICC.

Once the eSIM has been fully installed and provisioned (e.g., once thecommon SIM information and the personalized SIM information have beeninstalled in the eSIM), the UE device may be configured to access acarrier network. In particular, the UE device may be configured toaccess the carrier network of the service provider which provided theeSIM, in some embodiments.

In some embodiments, it may be desirable to re-provision or provideadditional provisioning for the eSIM in the UE device, e.g., at a latertime. For example, a user may desire to switch service providers, or toreceive service from multiple service providers for their UE device.

Thus, in some embodiments, the UE device may transmit a second requestfor provisioning information for the eSIM. The second request forprovisioning information may be a request for second common SIMinformation and second personalized SIM information or for secondpersonalized SIM information only, according to various embodiments.

The UE device may receive the second common SIM information and/orsecond personalized SIM information and install the second common SIMinformation and/or second personalized SIM information in the same wayas with the original common SIM information and/or personalized SIMinformation, or in a different way, e.g., according to any of thevariations described above.

The UE device may also remove the original common SIM information and/orpersonalized SIM information from the eSIM in some embodiments, e.g., ifthe user is no longer a subscriber with the carrier which provided thefirst eSIM.

FIG. 5—Flow Diagram

FIG. 5 illustrates an exemplary flow representing a process forpersonalizing an eSIM according to one embodiment. The embodimentillustrated in FIG. 5 is provided as an example of one possibleimplementation flow, however, it will be recognized that any number ofvariations or alternatives may be used as desired, and that theexemplary embodiment shown in FIG. 5 and described with respect theretoshould not be considered limiting to the disclosure as a whole.

As shown, the process may involve a UE device 502, an eSIM server 510, apersonalization server 512, and a home location register (HLR) andprovisioning system 514. The UE device may include a UICC or eUICC 504,which may interact with a baseband (BB) layer 506, which may in turninteract with an application processor (AP) 508.

The UE device 502 may send a request for an eSIM to the eSIM server 510.The eSIM server 510 may provide the UE device 502 with common SIMinformation for the eSIM. The UE device 502 may install the common SIMinformation portion of the eSIM and provide an indication that thecommon SIM information portion of the eSIM has been installed to theeSIM server 510.

Once the eSIM server 510 has received this indication, the eSIM servermay send a personalization request to the personalization server 512.The personalization server may be in contact with the HLR/provisioningsystem 514 and may send an indication thereto that service for aparticular set of personalized SIM information should be activated. TheHLR/provisioning system 514 may accordingly activate service for thatset of personalized SIM information and, once successful, may send anindication of that success to the personalization server 512.

The personalization server 512 may then provide a data blob includingthe personalized SIM information (e.g., an IMSI, a key, a PIN, and aPUK, according to one embodiment) to the eSIM server 510. The eSIMserver 510 may then provide the data blob to the UE device 502, whichmay provision its eSIM with the personalized SIM information.

The UE device 502 may then provide an indication of its success to theeSIM server 510 and/or the personalization server 512. Once the UEdevice 502 has been provisioned according to this process, the UE devicemay be able to access the carrier's network and perform wirelesscommunications using the fully configured eSIM.

Embodiments of the present disclosure may be realized in any of variousforms. For example some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of a methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a computer system may be configured to include aprocessor (or a set of processors) and a memory medium, where the memorymedium stores program instructions, where the processor is configured toread and execute the program instructions from the memory medium, wherethe program instructions are executable to implement any of the variousmethod embodiments described herein (or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets). Thecomputer system may be realized in any of various forms. For example,the computer system may be a personal computer (in any of its variousrealizations), a workstation, a computer on a card, anapplication-specific computer in a box, a server computer, a clientcomputer, a hand-held device, a tablet computer, a wearable computer,etc.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

We claim:
 1. A non-transitory computer readable medium storinginstructions that, when executed by a processor included in a userequipment (UE) device, cause the UE device to provision an embeddedsubscriber identity module (eSIM), by carrying out steps that include:obtaining common SIM information, wherein the common SIM informationcomprises non-subscriber-specific information that is common to aplurality of SIMS; transmitting, to a server, a request for personalizedSIM information, wherein the personalized SIM information comprisessubscriber-specific information; receiving, from the server, thepersonalized SIM information; and installing the personalized SIMinformation in an eSIM on the UE device, wherein the common SIMinformation and the personalized SIM information are configured toprovision the eSIM on the UE device.
 2. The non-transitory computerreadable medium of claim 1, wherein the personalized SIM information isconfigured to provision the eSIM on the UE device with thesubscriber-specific information.
 3. The non-transitory computer readablememory of claim 1, wherein the personalized SIM information comprisesone or more of: an International Mobile Subscriber Identity (IMSI)number; a personal identification number (PIN); a personal unblockingkey (PUK); and an authorization key (K).
 4. The non-transitory computerreadable medium of claim 1, wherein the personalized SIM information isencrypted, and the steps further include: decrypting the personalizedSIM information.
 5. The non-transitory computer readable medium of claim1, wherein the server comprises a personalization server.
 6. Thenon-transitory computer readable medium of claim 1, wherein the stepsfurther include: transmitting a request for common SIM information;receiving the common SIM information; and installing the common SIMinformation in the eSIM on the UE device.
 7. The non-transitory computerreadable medium of claim 6, wherein the common SIM information isreceived from an eSIM server, and the personalized SIM information isreceived from a personalization server.
 8. The non-transitory computerreadable medium of claim 7, wherein the request for common SIMinformation and the request for personalized SIM information aretransmitted to the eSIM server, and the eSIM server provides the requestfor personalized SIM information to the personalization server.
 9. Thenon-transitory computer readable medium of claim 1, wherein the commonSIM information is configured to provision the eSIM on the UE devicewith the non-subscriber-specific information.
 10. The non-transitorycomputer readable memory medium of claim 1, wherein the eSIM comprisescommon SIM information, and the common SIM information is pre-installedin the eSIM on the UE device.
 11. A method for provisioning an embeddedsubscriber identity module (eSIM) in a user equipment (UE) device, themethod comprising: at the UE device: obtaining common SIM information,wherein the common SIM information comprises non-subscriber-specificinformation that is common to a plurality of SIMs; transmitting, to aserver, a first request for provisioning information for the eSIM;receiving, from the server, first personalized SIM information inresponse to the first request for provisioning information for the eSIM,wherein the first personalized SIM information comprisessubscriber-specific information; and installing the first personalizedSIM information in the eSIM, wherein the common SIM information and thefirst personalized SIM information are configured to provision the eSIMon the UE device.
 12. The method of claim 11, the method furthercomprising: subsequent to installing the first personalized SIMinformation in the eSIM: transmitting a second request for provisioninginformation for the eSIM; receiving second personalized SIM informationin response to the second request for provisioning information for theeSIM; and installing the second personalized SIM information in theeSIM.
 13. The method of claim 12, wherein the second request comprises arequest to re-provision the eSIM, and the method further comprises:removing the first personalized SIM information from the eSIM.
 14. Themethod of claim 12, wherein the second request comprises a request foradditional provisioning for the eSIM, and the UE device comprises boththe first personalized SIM information and the second personalized SIMinformation after installing the second personalized SIM information inthe eSIM.
 15. A user equipment (UE) device, wherein the UE device isconfigured to provision a subscriber identity module (SIM) in the UEdevice, and the UE device comprises: one or more antennas for performingwireless communication; a processor; a memory storing instructions that,when executed by the processor, cause the processor to carry out stepsthat include: obtaining common SIM information, wherein the common SIMinformation comprises non-subscriber-specific information that is commonto a plurality of SIMS; transmitting, to a server, a request forpersonalized SIM information via a network, wherein the personalized SIMinformation comprises subscriber-specific information; receiving, fromthe server, the personalized SIM information via the network; andinstall installing the personalized SIM information in a SIM on the UEdevice, wherein the common SIM information and the personalized SIMinformation are configured to provision the SIM on the UE device. 16.The UE device of claim 15, wherein the UE device further comprises aremovable smart card, and the steps further include: installing thepersonalized SIM information on the removable smart card.
 17. The UEdevice of claim 15, wherein the UE device further comprises an embeddedsmart card, and the steps further include: installing the personalizedSIM information on the embedded smart card.
 18. The UE device of claim15, wherein the SIM is stored in a memory of the UE device, wherein theSIM is executable by the processor.
 19. The UE device of claim 15,wherein the UE device is configured to wirelessly transmit the requestfor personalized SIM information and receive the personalized SIMinformation using the one or more antennas.
 20. The UE device of claim15, wherein the network comprises a cellular service provider's network;and wherein the UE device is configured with a bootstrap SIM, and thebootstrap SIM provides the UE device with limited wireless access to thecellular service provider's network for the purpose of provisioning theSIM in the UE device.